(Note: The origin of this information may be internal or external to Novell. Novell makes every effort within its means to verify this information. However, the information provided in this document is FOR YOUR INFORMATION only. Novell makes no explicit or implied claims to the validity of this information.)
TITLE: Installing Paradox 3.5
DOCUMENT ID#: FYI.P.6047
DATE: 03Dec92
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: NA
SYMPTOM: NA
ISSUE/PROBLEM
Installing Paradox 3.5
Before Beginning
To install Paradox 3.5 on a Netware Lite network you must perform the steps described below. Please read this entire document before beginning the installation. By doing so you will get a better understanding of the process. You may also discover that some of the steps have already been done and do not need to be repeated. However, if you run into problems, try starting from the beginning and redoing all of the steps.
The installation is divided into three parts. The first part is the preparation of the server. The second part is the installation/configuration of Paradox. The third part is setting up the users. Any text which is shown between quotes (" ") is an example of what you would enter on the keyboard to perform the step being described. The text can be entered in either uppercase or lowercase. Do not type the quotes.
Prepare the Server
Please refer to the NetWare Lite manual, README.TXT file, or other fax documents if you need more information to complete any of the following steps.
1) Install Netware Lite on the machine that will be the file server. Select "Make this machine a client and a server." After NetWare Lite is installed, reboot the machine and load the network by typing "startnet" at the dos prompt. Be sure to run SHARE.EXE whenever the network is loaded. Test the network to make sure it is functioning properly. As a minimum, you should use the "Verify network connections" option in the NetWare Lite installation program.
2) Increase files handles and client tasks. The number of file handles is determined by the FILES= command in the CONFIG.SYS file. Use the NET utility to increase the client tasks for the server. This is done by selecting "Supervise the network," then "Server configuration," then "Client tasks." These modifications will take effect the next time the server is booted.
3) Create directories on the server's local drive where Paradox will be installed. You will need to create separate directories for the Paradox program files and the Paradox network control file. Also create a users directory where each user's "home" directory will be located. As an example, execute the following commands at the dos prompt (assuming that the c:\apps directory already exists):
"md c:\apps\pdox35"
"md c:\apps\pdox35\pdoxdata"
"md c:\users"
We will refer to these directory names throughout this document, however these names are only examples. If you want to use different directory names, simply substitute them for the names we have used. You may also use different drive letters than the ones we have used if you prefer. However, if you run into problems, try using the names and letters used in this document.
4) Create separate network directories for the Paradox program files and network control file. The procedure for completing this step is as follows:
a) Make sure the network is running and login as supervisor (or any other account with supervisor privileges).
b) Type "net" at the dos prompt to start the NET utility.
c) Highlight "Supervise the network" using the arrow keys and press the enter key.
d) Highlight "Network directories" and press the enter key.
e) Press the insert key to add a new network directory.
f) Highlight the name of the server where Paradox will be installed and press the enter key.
g) Enter a name for the network directory where the Paradox program files will be located, such as "pdox35."
h) Enter the complete path where the Paradox program files reside on the server. In our example this would be entered as "c:\apps\pdox35."
i) Leave the "Default access rights" as "ALL." Press the escape key, then press the enter key to save the new network directory definition.
j) Repeat steps e through i to define a second network directory for the Paradox network control file. Use "pdoxdata" for the network directory name and "c:\apps\pdox35\pdoxdata" for the path.
k) Repeat steps e through i to define a network directory to be used as the users directory. Use "users" for the network directory name and "c:\users" for the path.
l) Press Alt-F10 to exit the NET utility.
Install Paradox
If Paradox is already installed skip to the next paragraph, otherwise, install Paradox on the server's local drive according to the documentation supplied with Paradox. You will be installing Paradox as a network application, but not to a network directory. When prompted for drive letters and paths, use the appropriate local drive letters and paths as though you were installing Paradox as a stand-alone application. During the installation you will be prompted for information specific to your setup, like what type of network type you are using. Consult the Paradox documentation if you require additional information about how to respond to specific questions. Answers to critical questions are shown below.
Network type 6 (Other)
Network control file: c:\apps\pdox35\pdoxdata
Set Up the Users
Paradox allows each user to have a custom configuration for their paradox session. To use this feature you must create separate a directory for each user who will use a custom configuration. Create a user directory for each user by entering the following command at the dos prompt:
"md c:\users\username"
Where each person's name would be substituted for "username." In our example we show you how to set up user directories on the server. User directories can be set up on the workstations but must be done from each workstation.
Next, prepare to update the paradox network control file and change the attributes of the Paradox executable files to "read-only" by entering the following commands at the dos prompt:
"subst h: c:\apps\pdox35"
"subst i: c:\apps\pdox35\pdoxdata"
"h:"
"attrib +r *.exe"
"nupdate"
If you get a "command or filename not found" message trying to execute either the SUBST or ATTRIB command, make sure that the directory where they reside are in your current path.
You must also run the Paradox Custom Configuration Program (CCP) to create a PARADOX.CFG for each user. Whether you make user directories on the server or on each workstation, the directories must exist before starting the CCP. See Chapter 14 of the Paradox Users Guide if you require more information on how to use the CCP. The basic steps are outlined below.
1) Start the CCP by entering the following command at the dos prompt:
"paradox custom"
2) Once in the CCP, select "Net|SetPrivate" from the main menu.
3) Enter the path to the user's directory, such as "c:\users\<username>." The directory you specify must exist before starting the CCP.
4) Press "F2" to save the configuration. Choose "Network" when it prompts you for where to save the PARADOX.CFG file.
Repeat steps 1 through 4 for each user.
Starting Paradox from a Workstation
The easiest way for a user to start Paradox is to create a batch file which includes the following commands:
"net map h: pdox35"
"net map i: pdoxdata"
"net map j: users\%1"
"set t=%path%"
"path h:\;%path%"
"j:"
"paradox -share"
"path %t%"
After the network software has been loaded at the workstation and the user has logged in, the batch file should be executed. If the batch file were called PDOX.BAT, the user would type "pdox <username>" at the dos prompt, substituting the name of his or her user directory for <username>. <username> gets substituted for "%1" in the batch file.
Starting Paradox on the Server
To start Paradox on the server, create a batch file as in the paragraph above on starting from a remote node. Modify the batch file as follows:
"subst h: c:\apps\pdox35"
"subst i: c:\apps\pdox35\pdoxdata"
"cd c:\users\%1"
"set t=%path%"
"path h:\;%path%"
"paradox -share"
"path %t%"
"subst h: /d"
"subst i: /d"
This batch file can be run on the server whether or not the network software has been loaded. If the batch file were named PDOX.BAT, the user would enter "pdox <username>" at the dos prompt, substituting the name of his or her user directory for <username>. <username> gets substituted for "%1" in the batch file.
